@blueorangutan package

@GabrielBrascher a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✔centos7 ✖debian. JID-1649

Needs separate systemvm build if necessary
cc @DaanHoogland

Checked this, just URL/checksum change. Full smoketests not necessary, @GabrielBrascher have you found any reason we should build a new systemvmtemplate towards 4.15 release? Or keep using the build from June: http://download.cloudstack.org/systemvm/4.15/ cc @wido @DaanHoogland

@GabrielBrascher change gtm.
Do we expect debian to just remove older 10 releases when they update? This may lead to failures after we release as well. At least for anybody building their own systemVMs. What if we release and the day after they upgrade to 10.6?

@rhtyd this happened while I was building a System VM template for testing Python3 development at PR #3730.
Depending on how #3730 progress we might or might not need a new template.

@DaanHoogland I was thinking the same. Do we need to constantly update that any time that there is another Debian 10.X?

That might be interesting thinking about new developers playing around with the system VM template. However, it might require some manual effort to keep it up to date.

I like the idea but it will require designing a solution and might not be worth the effort. my question is mainly do we need this update now or do we wait till we know we need it?

@DaanHoogland that is a good question. What do you think @rhtyd?

I can close this PR if you guys think it should be addressed inside a PR when the respective requires a new system VM template.

The downside is that it could catch some developer that is not used with the building template process; but on the other hand, we don't need to keep an eye looking for changes on the Debian 10.X.Y.

Alternatives that I see:

1. Update iso just if a new template is necessary
2. Create some fancy way to automatically update
3. Update at any time if someone struggle with building and sees it (no automation checking from time to time the ISO)

if you need it you need it and i am fine with it. lgtm in that respect. i do not like the flimsy procedure we use, but i can live with it.

The systemvm py scripts are patched via systemvm.iso, so we don't need a new template unless there's something in the 10.5 update. I'll merge this as it breaks build and review/compare changes against the June build.